Description

Completes the documentation, Storybook, and test surface for the 2nd-gen progress bar migration, and adds the 1st-gen deprecation warnings for the properties that change in 2nd-gen. Also updates the migration-api skill so future migrations add runtime deprecation warnings alongside @deprecated JSDoc.

Motivation and context

The base migration branch landed the 2nd-gen component; this change finishes the consumer-facing surface (docs, stories, tests) and ensures 1st-gen consumers get runtime deprecation guidance for the APIs that changed, not just IDE-only JSDoc.

Related issue(s)

• fixes SWC-1776
• fixes SWC-1777
• fixes SWC-1778
• Part of the progress bar migration (parent: SWC-1769)

Screenshots (if appropriate)

Author's checklist

• I have read the CONTRIBUTING and PULL_REQUESTS documents.
• I have reviewed at the Accessibility Practices for this feature, see: Aria Practices
• I have added automated tests to cover my changes.
• I have included a well-written changeset if my change needs to be published. (The 1st-gen deprecation warnings are publishable — add a patch changeset for @spectrum-web-components/progress-bar if this targets a release branch.)
• I have included updated documentation if my change required it.

Reviewer's checklist

• Includes a Github Issue with appropriate flag or Jira ticket number without a link
• Includes thoughtfully written changeset if changes suggested include patch, minor, or major features
• Automated tests cover all use cases and follow best practices for writing
• Validated on all supported browsers
• All VRTs are approved before the author can update Golden Hash

Manual review test cases

• 1st-gen progress-bar unit tests pass, including deprecation warnings

  1. From repo root: cd 1st-gen
  2. Run yarn build && yarn test:start --group progress-bar
  3. Expect all tests pass; label/side-label/progress deprecation warnings fire only in dev mode with the expected data shape

• 2nd-gen progress-bar docs page renders

  1. Run Storybook for 2nd-gen/packages/swc
  2. Open Progress Bar → Docs
  3. Expect Anatomy, Options, States, Behaviors, and Accessibility sections to render with no console errors and no duplicate Docs entry

• 2nd-gen progress-bar tests pass on all engines

  1. From 2nd-gen/packages/swc
  2. Run VITEST_BROWSER_INSTANCES=chromium,firefox,webkit yarn vitest --run --project storybook progress-bar
  3. Expect all tests pass, including DescriptionPresentTest on WebKit

Device review

• Did it pass in Desktop?
• Did it pass in (emulated) Mobile?
• Did it pass in (emulated) iPad?

Accessibility testing checklist

• Keyboard (required — document steps below)

  1. Open the Progress Bar docs page in Storybook
  2. Tab through the page
  3. Expect the progress bar to be skipped (not focusable) and the surrounding focus order to be unaffected

• Screen reader (required — document steps below)

  1. Open the Anatomy, Indeterminate, and description-slot examples with VoiceOver (Safari) and NVDA (Firefox)
  2. Navigate to each progress bar
  3. Expect: progressbar role announced; accessible name from the label slot or accessible-label; aria-valuenow/aria-valuetext read for determinate bars and suppressed for indeterminate; description slot announced via aria-describedby when present and not announced once removed